Add auth0 source function #70
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey folks! Success Eng has received several tickets in the past couple of weeks related to logs from a tool called Auth0 and how those events can be pulled into Segment. The data that Auth0 sends out as logs doesn't follow the format Segment's ingestion API expects. As such, payloads can be dropped or data is not passed in its entirety to warehouses and/or other destinations where customers would like to use it.
Auth0 has deprecated their integration with Segment and all other third-party extensions but they have an option to send logs downstream via webhook. As such, I've written a quick Source Function to help customers more easily send Auth0 logs to Segment.